Genix Deployment Architecture - Azure MT

The following figure depicts the architecture of Azure PaaS deployment model (ABB or Customer owned).

The Azure deployment comprises of the following main sections:

• Genix Edge Platform (Southbound) - Genix Edge

• Genix Analytics Platform (Northbound)

Genix Edge Platform Deployment

Genix Edge is deployed and configuration is done through remote edge management portal from ABB Ability cloud platform.

Edges are deployed in tenant's LAN network and connected to Genix northbound via internet (VPN is not required).

There can be edges at L3 or L4 network of tenant's network. Also, there can be one or more edges at each network.

Genix Analytics Platform

Some of the components on northbound support infrastructure are shared to optimize cost of deployment.

Infrastructure sharing is possible for the following components:

• Azure Kubernetes Cluster - Each tenant's deployment goes into a specific namespace. Sizing is done as per the deployment size considering all tenants. Scaling is increased as and when the tenants are added.

• Azure Elastic Pool SQL DB - Each tenant's ICM deployment goes into a specific database on single SQL Server. There is cap on volume - overall 4 TB per pool, if there are volume constraints, then dedicated database per tenant model is considered.

• Azure Application Gateway - Configured with URL based routing for each tenant. Sizing is done as per the number of users and bandwidth requirements.

Rest of the components are one service/component per tenant. For information about the list of deployable components, see Infrastructure Requirements.